Skip to content

Conversation

@dumbbell
Copy link
Collaborator

Why

rabbit_access_control now ensures all configured auth backend modules are provided by rabbit or an enabled plugin. This is not the case for this testsuite's own auth backend.

How

Declare rabbit_auth_backend_context_propagation_mock as a test auth backend module.

…st auth backend module

[Why]
rabbit_access_control now ensures all configured auth backend modules
are provided by `rabbit` or an enabled plugin. This is not the case for
this testsuite's own auth backend.

[How]
Declare `rabbit_auth_backend_context_propagation_mock` as a test auth
backend module.
@dumbbell dumbbell added this to the 4.3.0 milestone Oct 21, 2025
@dumbbell dumbbell self-assigned this Oct 21, 2025
@michaelklishin
Copy link
Collaborator

@dumbbell I like the idea.

FTR, the relevant core part this change relies on is rabbit_access_control.erl#L158.

@dumbbell dumbbell marked this pull request as ready for review October 23, 2025 17:28
@dumbbell dumbbell merged commit 1df3b64 into main Oct 23, 2025
576 of 577 checks passed
@dumbbell dumbbell deleted the fix-unit_access_control_authn_authz_context_propagation_SUITE branch October 23, 2025 17:29
michaelklishin added a commit that referenced this pull request Oct 23, 2025
unit_access_control_authn_authz_context_propagation_SUITE: Declare test auth backend module (backport #14767)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants